UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

MarkLogic Server must implement NIST FIPS 140-2 or 140-3 validated cryptographic modules to provision digital signatures.


Overview

Finding ID Version Rule ID IA Controls Severity
V-220414 ML09-00-012000 SV-220414r879885_rule Medium
Description
Use of weak or untested encryption algorithms undermines the purposes of utilizing encryption to protect data. The application must implement cryptographic modules adhering to the higher standards approved by the federal government since this provides assurance they have been tested and validated. For detailed information, refer to NIST FIPS Publication 140-2 or Publication 140-3, Security Requirements for Cryptographic Modules. Note that the product's cryptographic modules must be validated and certified by NIST as FIPS-compliant.
STIG Date
MarkLogic Server v9 Security Technical Implementation Guide 2024-01-24

Details

Check Text ( C-22129r863307_chk )
Check MarkLogic configuration to verify use of NIST FIPS validated cryptographic modules to provision digital signatures.

Perform the check from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges.

1. Click the Clusters icon.
2. Click the local cluster.
3. If SSL FIPS enabled button is false, this is a finding.
Fix Text (F-22118r863308_fix)
Configure MarkLogic to use NIST FIPS validated cryptographic modules to provision digital signatures.

Perform the fix from the MarkLogic Server Admin Interface with a user that holds administrative-level privileges.

1. Click the Clusters icon.
2. Click the local cluster.
3. Enable SSL FIPS option.